Add note on available api/data files for peps #4783
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hugovk
reviewed
Jan 16, 2026
hugovk
reviewed
Jan 16, 2026
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
scutuatua-crypto
approved these changes
Jan 17, 2026
encukou
reviewed
Jan 19, 2026
Comment on lines
+28
to
+33
| - `peps.json <https://peps.python.org/api/peps.json>`_: All PEP metadata | ||
| - `release-cycle.json <https://peps.python.org/api/release-cycle.json>`_: Python release cycle information | ||
| - `python-releases.json <https://peps.python.org/api/python-releases.json>`_: Complete Python release history | ||
| - `release-schedule.ics <https://peps.python.org/release-schedule.ics>`_: Python release dates in calendar format | ||
|
|
||
|
|
Member
There was a problem hiding this comment.
Do we want to duplicate the list here? If so we might want comments in both places reminding people to keep them in sync.
Member
There was a problem hiding this comment.
Good point, let's make it easy for ourselves and just link to the main page.
hugovk
reviewed
Jan 19, 2026
Comment on lines
+26
to
+31
| Several data files are available at https://peps.python.org/api/: | ||
|
|
||
| - `peps.json <https://peps.python.org/api/peps.json>`_: All PEP metadata | ||
| - `release-cycle.json <https://peps.python.org/api/release-cycle.json>`_: Python release cycle information | ||
| - `python-releases.json <https://peps.python.org/api/python-releases.json>`_: Complete Python release history | ||
| - `release-schedule.ics <https://peps.python.org/release-schedule.ics>`_: Python release dates in calendar format |
Member
There was a problem hiding this comment.
Suggested change
| Several data files are available at https://peps.python.org/api/: | |
| - `peps.json <https://peps.python.org/api/peps.json>`_: All PEP metadata | |
| - `release-cycle.json <https://peps.python.org/api/release-cycle.json>`_: Python release cycle information | |
| - `python-releases.json <https://peps.python.org/api/python-releases.json>`_: Complete Python release history | |
| - `release-schedule.ics <https://peps.python.org/release-schedule.ics>`_: Python release dates in calendar format | |
| Several data files are available at https://peps.python.org/api/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently learned there was a calendar output for the release cycle based on PEPs data.
I didn't know this, so we should document it!
📚 Documentation preview 📚: https://pep-previews--4783.org.readthedocs.build/